Network synchronization system and information processing device

ABSTRACT

In a network synchronization system including plural information processing devices, a first information processing device includes a synchronization-use common storage unit configured to copy and store first information for each user authorized to use the first information processing device, so that the first information can be shared with another information processing device; and a second information processing device includes a setting information unit configured to store second information for each user authorized to use the second information processing device, and a synchronization control unit configured to compare the second information with the first information, and to update the second information to latest information based on a result of the comparison. The synchronization control unit acquires common update information common to the information processing devices, which is stored in the synchronization-use common storage unit.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a network synchronization system and aninformation processing device.

2. Description of the Related Art

The recent years have witnessed the development of an informationprocessing system including an information processing device connectedto a network, which performs communications with plural informationdevices to exchange documents in various data formats by applying pluralcommunication protocols.

In such an information processing system, various application servicesare provided through the information processing device. The variousapplication services include sending an image obtained by scanning anoriginal document or data created by an information device to aspecified destination by e-mail, sending this information by facsimiletransmission, and transferring files containing this information to aninformation device; and recording/outputting the text of a receivede-mail or an image of a file attached to the e-mail, sending thisinformation to a specified fax machine, and transferring filescontaining this information to an information device; andstoring/managing data in the information processing device.

However, such an information processing device needs to be connectedwith plural information devices via a network. When plural devices thatrequire authentication are separately provided in the network and eachof the devices has a function of identifying an individual and allowingonly a registered user to use the device, the user needs to input a username and a password for each of the devices, which is not user-friendly.One approach is to integrate the devices in the system, so that only asingle user name and a single password are required. However, when theauthentication information is already being separately managed, enormouscosts would be incurred in order to establish a system for managing theauthentication information in an integrated manner.

The invention disclosed in patent document 1 is a network communicationssystem including a document input/output device providing a function ofidentifying an individual by an authentication operation performed withan operations unit and allowing only a registered user to use thedevice, and plural external devices which are connected via a network,providing a function of identifying individuals with a protocol of thenetwork.

The document input/output device according to the invention of patentdocument 1 is capable of automatically authenticating external devices.Specifically, in order to execute all of the authentication operationsof the authentication units that are separately provided in the externaldevices, only one authentication operation needs to be performed withthe operations unit of the document input/output device.

Patent Document 1: Japanese Laid-Open Patent Application No. 2007-67830

When developing a network communications system including pluralinformation processing devices such as the document input/output devicedisclosed in patent document 1, the following aspect is preferablyaddressed. For example, in a network communications system includinginformation processing devices used by staff members belonging to acertain organization in a company, the setting information items such asuser information items that are registered in the respective informationprocessing devices are preferably the same (in synchronization).

However, with the conventional technology, enormous costs would berequired to establish such a system, i.e., a system for managing thesetting information set in the respective devices in an integratedmanner.

SUMMARY OF THE INVENTION

The present invention provides a network synchronization system and aninformation processing device in which one or more of theabove-described disadvantages are eliminated.

A preferred embodiment of the present invention provides a networksynchronization system and an information processing device, with whichsetting information can be effectively synchronized among pluralinformation processing devices.

According to an aspect of the present invention, there is provided anetwork synchronization system including plural information processingdevices, wherein a first information processing device among the pluralinformation processing devices includes a synchronization-use commonstorage unit configured to copy and store first individual settinginformation for each user registered as being authorized to use thefirst information processing device, so that the first individualsetting information can be shared with another one of the pluralinformation processing devices other than the first informationprocessing device; and a second information processing device among theplural information processing devices includes a setting informationunit configured to store second individual setting information for eachuser registered as being authorized to use the second informationprocessing device, and a synchronization control unit configured tocompare the second individual setting information for each user storedin the setting information unit with the first individual settinginformation for the corresponding user stored in the synchronization-usecommon storage unit, and to update the second individual settinginformation to latest individual setting information for each user basedon a result of the comparison, wherein the synchronization control unitacquires common update information that is common to the pluralinformation processing devices, wherein the common update information isstored in the synchronization-use common storage unit.

According to an aspect of the present invention, there is provided aninformation processing device included in a network synchronizationsystem including plural information processing devices, the informationprocessing device including a setting information unit configured tostore first individual setting information for each user registered asbeing authorized to use the information processing device; and asynchronization control unit configured to compare the first individualsetting information for each user stored in the setting information unitwith second individual setting information for the corresponding userstored in a synchronization-use common storage unit included in anotherone of the plural information processing devices, and to update thefirst individual setting information for each user stored in the settinginformation unit to latest individual setting information for thecorresponding user based on a result of the comparison, wherein thesynchronization control unit is further configured to acquire commonupdate information that is common to the plural information processingdevices, wherein the common update information is stored in thesynchronization-use common storage unit included in the other one of theplural information processing devices.

According to one embodiment of the present invention, a networksynchronization system and an information processing device areprovided, with which setting information can be effectively synchronizedamong plural information processing devices.

BRIEF DESCRIPTION OF THE DRAWINGS

Other objects, features and advantages of the present invention willbecome more apparent from the following detailed description when readin conjunction with the accompanying drawings, in which:

FIG. 1 illustrates a configuration of a network synchronization systemaccording to a first embodiment of the present invention;

FIG. 2 is a functional block diagram of a multifunction peripheral (MFP)according to the first embodiment of the present invention;

FIG. 3 illustrates an example (part 1) of setting information that isthe target of network synchronization;

FIG. 4A through 4D illustrate an example (part 2) of setting informationthat is the target of network synchronization;

FIG. 5 is an example of synchronization setting information for networksynchronization;

FIG. 6 illustrates an example of a system configuration for describing anetwork synchronization operation;

FIG. 7 illustrates an example of setting information of a first MFP anda second MFP before network synchronization;

FIG. 8 illustrates an example of setting information of a first MFP anda second MFP after network synchronization;

FIG. 9 is a flowchart of an example of a first operation of a networksynchronization operation;

FIG. 10 is a flowchart of a detailed example of step S3 in FIG. 9;

FIG. 11 is a flowchart of an example of a second operation of thenetwork synchronization operation;

FIG. 12 is a flowchart of a detailed example of step S23 in FIG. 11;

FIG. 13 illustrates an example of setting information of a first MFP anda second MFP before network synchronization according to a firstmodification;

FIG. 14 illustrates an example of setting information of a first MFP anda second MFP after network synchronization according to the firstmodification;

FIG. 15 illustrates an example of setting information of a first MFP anda second MFP before network synchronization according to a secondmodification;

FIG. 16 illustrates an example of setting information of a first MFP anda second MFP after network synchronization according to the secondmodification;

FIG. 17 is a functional block diagram of an MFP according to a secondembodiment of the present invention;

FIG. 18 illustrates an example of synchronization setting informationused for network synchronization;

FIG. 19 is a flowchart of an example of a synchronization process(downloading via the download server) according to the second embodimentof the present invention;

FIG. 20 is a flowchart of an example of a synchronization process(downloading via network synchronization) according to the secondembodiment of the present invention;

FIG. 21 is a block diagram of an MFP according to a third embodiment ofthe present invention;

FIG. 22 is a functional block diagram of the MFP according to the thirdembodiment of the present invention;

FIG. 23 is a flowchart of an example of an operation performed by theMFP according to the third embodiment of the present invention;

FIG. 24 illustrates an example of acquired image information; and

FIGS. 25A through 25C illustrate processes of outputting or storingimage information acquired according to identification information.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

A description is given, with reference to the accompanying drawings, ofembodiments of the present invention.

A multifunction peripheral is taken as an example of an informationprocessing device according to an embodiment of the present invention.The multifunction peripheral includes multiple functions such as a copyfunction, a fax function, a printer function, a scanner function, and afunction for distributing an input image (an image obtained by scanningan original with the scanner function or an image input by the printerfunction or the fax function). However, the present invention is notlimited to a multifunction peripheral. The present invention isapplicable to any other typical computer device.

First Embodiment

A description is given of a first embodiment according to the presentinvention with reference to FIGS. 1 through 11.

(Example of System Configuration)

FIG. 1 illustrates a configuration of a network synchronization systemaccording to the first embodiment of the present invention. As shown inFIG. 1, a network synchronization system 1 includes plural multifunctionperipherals (MFPs) 2 a, 2 b, 2 c, and 2 d (hereinafter, simply referredto as “MFP 2” when indicating one of these MFPs) which areinterconnected via a network such as LAN (Local Area Network), and aninformation processing server 3.

As described above, the MFP 2 is an image processing device includingmultiple functions such as a copy function, a fax function, a printerfunction, a scanner function, and a function for distributing an inputimage (an image obtained by scanning an original with the scannerfunction or an image input by the printer function or the fax function).

The information processing server 3 is a computer device, whichfunctions as a user information management server for managing, in anintegrated manner, user information including user names and passwordsof the users using the network synchronization system 1, and whichacquires various information items such as antivirus definitioninformation from an external device (not shown). Plural informationprocessing servers can be provided according to the usage purpose.

With the above system configuration, in the network synchronizationsystem 1 according to the first embodiment, setting information in theplural MFPs 2 can be effectively synchronized (hereinafter,synchronization according to an embodiment of the present invention isreferred to as “network synchronization”).

(Example of Functional Configuration of Network Synchronization ofSetting Information)

FIG. 2 is a functional block diagram illustrating the networksynchronization of the setting information of the MFP. As shown in FIG.2, the MFP 2 includes a setting information unit 210, asynchronization-use common storage unit 220, a synchronization settinginformation unit 230, and a synchronization control unit 240.

The setting information unit 210 is a storage device in the MFP 2 forstoring setting information. The setting information (individual settinginformation) is specified for each user registered as being authorizedto use the corresponding MFP 2, although the present invention is not solimited. Specific examples are given below with reference to FIGS. 3 and4.

The synchronization-use common storage unit 220 is a storage device forstoring setting information that is the target of networksynchronization in the network synchronization system 1. The settinginformation that is the target of network synchronization is, forexample, the setting information stored in the setting information unit210. The information stored in the setting information unit 210 iscopied into the synchronization-use common storage unit 220. When thesynchronization setting information unit 230 described below has made asetting of “disclose” in the item for specifying whether to “disclosesynchronization-use common folder (synonymous to synchronization-usecommon storage unit)”, the user can access the synchronization-usecommon storage unit 220 of a certain MFP 2 from another MFP 2. That is,when a setting of “disclose” is set in the item for specifying whetherto “disclose synchronization-use common folder” in a second MFP 2 thatis provided with a synchronization-use common storage unit 320, a firstMFP 2 can access the synchronization-use common storage unit 320 of thesecond MFP 2 to acquire the setting information of the second MFP 2.

The synchronization setting information unit 230 is a storage device forstoring synchronization setting information which specifies operationsof network synchronization. An example of the synchronization settinginformation is described below with reference to FIG. 5.

The synchronization control unit 240 implements various controloperations pertaining to network synchronization based onsynchronization setting information stored in the synchronizationsetting information unit 230. A CPU (Central Processing Unit) implementsthe control operations based on a program (synchronization controlprogram) installed in the MFP 2.

With the above functional configuration, the network synchronizationsystem 1 according to the first embodiment can effectively performnetwork synchronization for the setting information in the plural MFPs 2(particularly, the setting information of each of the users registeredin the respective devices). Furthermore, when the setting information ofthe same user is separately managed in different MFPs 2, the separatelymanaged information items can be associated with each other (tiedtogether), and can be the appropriately synchronized.

Each of the setting information unit 210, the synchronization-use commonstorage unit 220, and the synchronization setting information unit 230may be constituted with two HDD sections having exactly the same formatfor storing setting information. One of the HDD sections may correspondto a storage unit for storing the setting information that is currentlybeing operated, and the other one of the HDD sections may correspond toa storage unit for storing the setting information obtained after thenetwork synchronization. Each time the network synchronization iscompleted, the currently-operated HDD section may be switched.Accordingly, the network synchronization results may be immediatelyreflected.

(Example of Setting Information that is Target of NetworkSynchronization)

FIGS. 3 and 4A through 4D illustrate examples (part 1) and (part 2) ofthe setting information that is the target of network synchronization.This setting information is stored in the setting information unit 210,and is copied into the synchronization-use common storage unit 220. Thesetting information may include individual (user) setting information asshown in FIG. 3, or registered user information, deleted userinformation, same-user information, and user authentication informationas shown in FIGS. 4A through 4D.

The individual setting information as shown in FIG. 3 is provided foreach user registered in the MFP 2, and therefore the number of sets ofindividual setting information is equal to the number of users (usuallyplural). Each of the sets of information shown in FIGS. 4A through 4D(the registered user information through the user authenticationinformation) corresponds to catalog information displaying a collectivelist of plural users.

First, a description is given of the “individual setting information”shown in FIG. 3. The “individual setting information” is a table formanaging setting information for each user registered as beingauthorized to use the corresponding device (self-device, i.e., self-MFP)or another device. A user registered in another device is includedbecause such a user will also be registered in the corresponding deviceas a result of the network synchronization according to an embodiment ofthe present invention.

The “user ID (unique)” is user identification information foridentifying the user in the self-device. For example, a unique user IDis determined internally based on a combination of time informationexpressing the time when the user first registered in the self-deviceand machine-specific information of the self-device (for example,network address (MAC address)).

The “furigana” is the hiragana corresponding to the kanji expressing theuser's name (in Japanese characters). “Division” is the name of thedivision to which the user belongs. The “individual name (unique)” isthe unique individual name of the user. This information is managed bythe information processing server 3.

The “user name (unique)” and the “password” are used by the user to loginto the self-device. The password is information that is to beperiodically renewed in consideration of safety, and is thus not uniquein this example.

The “IC card number (unique)” is used as authentication referenceinformation held by the self-device for performing authentication basedon an IC card when the user can log into the self-device with the use ofan IC card.

The “Windows (registered trademark) user name” and the “Windows(registered trademark) user password” are authentication informationused when authentication is performed for the user to enter theinformation processing server 3 (in this case, a Windows (registeredtrademark) server), i.e., an external server, to log into theself-device.

Next, a description is given of the “registered user information” shownin FIG. 4A. The “registered user information” is a table for managinginformation corresponding to the preference of each user that iscurrently registered in the self-device (or another device). Asdescribed above, this information corresponds to catalog informationdisplaying a collective list of plural users.

The “user ID” corresponds to the user ID of FIG. 3. The “user name”corresponds to the user name (unique) of FIG. 3. The “individual name”corresponds to the individual name (unique) of FIG. 3. The “last logindate (important)” is the date of the last time the user logged into theself-device. This information is automatically set in the self-devicewhen the user logged in the last time. The “last-update date(important)” is the date of the last time the user's individual settinginformation was updated in the self-device. This information isautomatically set in the self-device at the last time the informationwas updated. The “IC card number” corresponds to the IC card number ofFIG. 3. The “individual setting file” corresponds to the file includingthe individual setting information regarding the user shown in FIG. 3.The “individual setting file” is exchanged between the self-device andother devices; the data of the individual setting information in thefile can be compressed to facilitate the process of exchanging thisinformation.

The information corresponding to the preference of each user managed inthe “registered user information” is not limited to that shown in FIG.4A. For example, the information may include various contents such as afile of a document that the user stored in the self-device or a QR coversheet obtained by embedding the user ID into a QR code.

The “registered user information” is appropriately updated by performingnetwork synchronization according to an embodiment of the presentinvention. In addition to the “registered user information” that isupdated to the latest version, the setting information unit 210preferably stores plural versions of the “registered user information”,including the version corresponding to the previous update (and the“registered user information” corresponding to the update before theprevious update). This is to be prepared for recovery in the event thatan unpredicted error occurs.

Next, a description is given of the “deleted user information” shown inFIG. 4B. The “deleted user information” is a table functioning as amanaging unit for managing deleted users. As described above, thisinformation corresponds to catalog information displaying a collectivelist of plural users.

The “user ID” corresponds to the user ID (unique) shown in FIG. 3. The“deleted date (important)” is information specifying the date when theuser was deleted. This information is automatically set when the user isdeleted.

Next, a description is given of the “same-user information” shown inFIG. 4C. The “same-user information” is a table functioning as anassociating unit for associating setting information of the same usermanaged separately in the respective devices.

The “GUID” is unique identification information in the self-device (oranother device). For example, a unique “GUID” is determined internallybased on a combination of time information and machine-specificinformation of the self-device (for example, network address (MACaddress)). This is linking information for associating user IDs that areseparately registered in different devices. The “user ID” corresponds tothe user ID shown in FIG. 3.

For example, a user having a user name “TARO” may be given a user ID of“01 a” in one device and may be given a user ID of “01 b” in anotherdevice. Even when this is the case, by issuing a GUID of “A01”, which iscommon to both of these user IDs as shown in FIG. 4C, it can bedetermined that the user who is given the user ID of “01 b” and the userwho is given the user ID of “01 a” correspond to the same user.Accordingly, by providing “same-user information”, user IDs of the sameuser managed separately in different devices can be associated with eachother.

Next, a description is given of the “user authentication information”shown in FIG. 4D. The “user authentication information” is a tablefunctioning as a managing unit for managing, in a simple manner, thesetting information of each user whose user IDs are associated togetherin the “same-user information” table shown in FIG. 4C. The “userauthentication information” is created based on the same user list shownin FIG. 4C.

The “user ID” corresponds to the user ID shown in FIG. 3 in theself-device. The “remote user ID” corresponds to the user ID shown inFIG. 3 of the same user registered in another device.

For example, when the user with the user ID “01 b” attempts to log intoa device, but cannot use the user ID “01 b” to log into the device, thedevice can refer to the “same-user information” table and finds out thata GUID “A01” is assigned to the user ID “01 b”, and the GUID “A01” isalso assigned to the user ID “01 a”. Accordingly, the user with the userID “01 b” can log into the device as the user with the user ID “01 a”.

Meanwhile, in the “user authentication information” table, the “user ID”which is the user ID in the self-device and the “remote user ID” whichis the user ID in another device, are associated with each otherone-on-one. Accordingly, the device can find out that the user ID “01 a”and the user ID “01 b” are associated with each other, without referringto the GUID.

(Example of Synchronization Setting Information for NetworkSynchronization)

FIG. 5 is an example of synchronization setting information for networksynchronization. The synchronization setting information is stored inthe synchronization setting information unit 230. The synchronizationsetting information is system setting information unique to each of thedevices, and specifies settings for the network synchronizationaccording to an embodiment of the present invention.

Based on such synchronization setting information, the synchronizationcontrol unit 240 implements various control operations pertaining tonetwork synchronization. In the following, descriptions are given ofeach of the setting items shown in FIG. 5, in association with thecontrol operations performed by the synchronization control unit 240shown in FIG. 2.

First, a description is given of the “last-update date setting”. The“last-update date setting” is internally set when the settinginformation held in the self-device is updated.

The “last update time/date” is a setting item specifying the time/dateof updating the setting information held in the self-device the last(most recent) time due to network synchronization. This setting item isinternally set when the self-device performs network synchronization. Inorder to perform the network synchronization, the synchronizationcontrol unit 240 compares the last update time/date of the self-devicewith that of another device, and when the last update time/date of theother device is newer than that of the self-device, the synchronizationcontrol unit 240 updates the setting information of the self-device soas to correspond to that of the other device. Accordingly, theself-device can always hold the latest setting information. For example,when the network synchronization system 1 has three devices, including adevice A (last update time/date 10 o'clock), a device B (last updatetime/date 11 o'clock), and a device C (last update time/date 12o'clock), the setting information of the devices A and B is updated sothat all of the devices hold the setting information of the device C(last update time/date 12 o'clock).

Next, a description is given of “network synchronization setting”. The“network synchronization setting” specifies whether the self-device isto perform network synchronization, and also specifies thesynchronization intervals at which the self-device is to perform networksynchronization.

“(Perform or do not perform) network synchronization” is a setting itemspecifying whether the self-device is to perform “networksynchronization”. When “perform (network synchronization)” is set, thesynchronization control unit 240 can perform network synchronization.

“Disclose (or do not disclose) synchronization-use common folder(synonymous to synchronization-use common storage unit 220)” is asetting item specifying whether to disclose or to not disclose thesynchronization-use common folder of the self-device to the outside.When “disclose” is specified, devices other than the self-device canaccess the synchronization-use common folder of the self-device. Thatis, in another device provided with the synchronization-use commonstorage unit 320, when “disclose” is set in the item of “disclosesynchronization-use common folder”, the synchronization control unit 240(of the self-device) can access the synchronization-use common storageunit 320 (of the other device). In the present embodiment, “disclose” isset only for a single one of the MFPs 2 in the network synchronizationsystem 1.

The “network path (for example, displaying 1 through 1,024 characters)”is a setting item for specifying the location of the synchronization-usecommon folder of another device. With the use of this network path, thesynchronization control unit 240 can identify the location of asynchronization-use common folder (for example, the synchronization-usecommon storage unit 320) of another device. The self-device can have thefollowing configuration. That is, when “disclose” is set as the settingitem of “disclose synchronization-use common folder” in the self-device,the setting of the network path is made ineffective. This is becausewhen the synchronization-use common folder of the self-device isdisclosed to other devices, and there is no need to set such a networkpath. Conversely, the setting of the network path is made effective when“do not disclose” is set in the self-device.

“Login user name (for example, displaying 0 through 256 English one bytecharacters)” and “login password (for example, displaying 0 through 256characters)” are setting items for the login user name and the loginpassword, respectively, which are used for logging into thesynchronization-use common folder of the self-device. By using the“login user name” and the “login password” of another device, thesynchronization control unit 240 can connect to the synchronization-usecommon folder (for example, the synchronization-use common storage unit320) of the other device.

“Automatic synchronization interval (for example, 10 through 9,999minutes)” is a setting item for specifying synchronization intervals atwhich the self-device is to perform network synchronization with anotherdevice. The synchronization control unit 240 performs networksynchronization between the self-device and another device at automaticsynchronization intervals as specified. The automatic synchronizationintervals can be specified by the user. Furthermore, in order todistribute the network load, the probability according to random numberscan be calculated based on the machine-specific number and the presenttime, to determine the next synchronization time from a synchronizationinterval probability X.

The synchronization setting information shown in FIG. 5 is describedabove. The synchronization setting information is setting informationspecific to each of the devices. Based on such synchronization settinginformation, the synchronization control unit 240 implements variouscontrol operations pertaining to network synchronization. In thefollowing, a description is given of the control operations.

(Example of Network Synchronization Operations)

FIG. 6 illustrates an example of a system configuration for describingthe network synchronization operation. A description is given of anexample of network synchronization operations for synchronizing thesetting information, performed between the MFP 2 a (second device)(corresponding to self-device) that has newly joined the networksynchronization system 1, and the MFP 2 b (first device) that isdifferent from the self-device. It is assumed that the settinginformation schematically illustrated in FIG. 7 is stored beforehand inthe setting information unit 210 and a setting information unit 310 ofthe MFP 2 a and the MFP 2 b, respectively. As shown in FIG. 7, the user“TARO” is given different user IDs “01 a” and “01 b” in the MFP 2 a andthe MFP 2 b, respectively.

When the network synchronization operation ends, the setting informationshown in FIG. 7 changes to that shown in FIG. 8. By comparing FIGS. 7and 8, it can be found that in FIG. 8, the user ID “01 a” and the userID “01 b” have been associated with each other in the same-userinformation table of the MFP 2 b. Furthermore, as shown in FIG. 8, inthe MFP 2 a, the individual setting file of the user ID “01 a” has beenupdated from “File01 a” to “File01 b”, and a new user having a user ID“02 b” has been added. In the user authentication information table, theuser ID “01 a” and the user ID “01 b” have been associated with eachother.

In the present embodiment, the network synchronization operation isdescribed in the order of a first operation and a second operation. Thefirst operation is for performing synchronization of the settinginformation between the setting information unit 310 and thesynchronization-use common storage unit 320 in the MFP 2 b. The secondoperation is for performing synchronization between the MFP 2 a that hasnewly joined the network synchronization system 1 and the MFP 2 b(synchronization-use common storage unit 320). It is assumed that in theMFP 2 b, the setting item of “disclose synchronization-use commonfolder” is set as “disclose”. Accordingly, the MFP 2 a can access thesynchronization-use common storage unit 320 of the MFP 2 b.

(Network Synchronization Operation (First Operation))

First, a description is given of the first operation. FIG. 9 is aflowchart of an example of the first operation of the networksynchronization operation. FIG. 10 is a flowchart of a detailed exampleof step S3 in FIG. 9. A description is given of an example of a firstoperation, in which synchronization of setting information is performedbetween the setting information unit 310 and the synchronization-usecommon storage unit 320 in the MFP 2 b.

First, the MFP 2 b determines whether the time has reached thesynchronization start time (step S1). At this step, a synchronizationcontrol unit 340 makes the determination based on a setting of“automatic synchronization interval” which is stored in asynchronization setting information unit 330. When it is determined thetime has reached the synchronization start time (Yes in step S1), theflow proceeds to step S2. When it is determined that the time has notyet reached the synchronization start time (No in step S1), step S1 isrepeatedly performed.

In step S2, the MFP 2 b connects itself to the synchronization-usecommon storage unit 320 of the self-device (step S2). In this case, itmeans that in the MFP 2 b, the synchronization control unit 340 isconnected to the synchronization-use common storage unit 320.

In step S3, the MFP 2 b performs a synchronization process between itssynchronization-use common storage unit 320 (step S3). In this case, itmeans that in the MFP 2 b, the setting information stored in thesynchronization-use common storage unit 320 is updated based on thesetting information stored in the setting information unit 310.

Details of the process performed at step S3 are described with referenceto FIG. 10.

First, the MFP 2 b starts exclusive control (step S11). Thesynchronization control unit 340 creates a directory, for example, as aprocess of exclusive control. Specifically, before startingsynchronization, the synchronization control unit 340 creates adirectory in the synchronization-use common storage unit 320 of theself-device. Only a device that has succeeded in creating a directory isallowed to use the synchronization-use common storage unit 320.

In step S12, the MFP 2 b determines whether the exclusive control issuccessfully implemented (step S12). When the exclusive control issuccessfully implemented (Yes in step S12), the flow proceeds to stepS13. When the exclusive control is unsuccessful (No in step S12), itmeans that the synchronization is unsuccessful, and the process ends as“synchronization unsuccessful”.

In step S13, the MFP 2 b compares the setting information in thesynchronization-use common storage unit 320 of the self-device with thesetting information in the setting information unit 310 of theself-device (step S13). In this example, the synchronization-use commonstorage unit 320 does not store any setting information, and the flowproceeds to step S14, where the MFP 2 b updates the setting informationin the synchronization-use common storage unit 320 of the self-device tothe latest information (step S14). In this step, the setting informationstored in the setting information unit 310 is copied to thesynchronization-use common storage unit 320 of the self-device toupdate/convert the synchronization-use common storage unit 320.

When step S14 is completed, the flow proceeds to step S15, where the MFP2 b ends the exclusive control that has started in step S11 (step S15).The exclusive control ends as the synchronization control unit 340erases the directory created at step S11. As the synchronization issuccessful, the process ends as “synchronization successful”.

Referring back to FIG. 9, when the synchronization process at step S3 iscompleted, the flow proceeds to step S4, where the MFP 2 b determineswhether the synchronization process is successful (step S4). When thesynchronization process is successful (Yes in step S4), the flowproceeds to step S5. When the synchronization process is unsuccessful(No in step S4), the flow proceeds to step S7.

In step S5, the MFP 2 b releases the connection between thesynchronization-use common storage unit 320 of the self-device, whichhas started at step S2 (step S5). In this case, it means that in the MFP2 b, the synchronization control unit 340 is disconnected from thesynchronization-use common storage unit 320.

Next, in step S6, the MFP 2 b updates the setting information in thesetting information unit 310 of the self-device (step S6). Thesynchronization control unit 340 updates the setting information of thesetting information unit 310 based on the setting information in thesynchronization-use common storage unit 320 that has been updated to thelatest information. In this example, there is initially nothing storedin the synchronization-use common storage unit 320, and therefore thesetting information in the setting information unit 310 and thesynchronization-use common storage unit 320 is the same. Accordingly,step S6 can be skipped.

In step S6, in a case where the setting information unit 310 includesHDD sections having exactly the same format for storing the settinginformation, the synchronization results can be immediately reflected byswitching the HDD section that is currently operating. The HDD sectionis preferably switched when all of the users using the MFP 2 b havelogged out. When the process of step S6 is completed, the flow returnsto step S1 once again.

In step S7, the MFP 2 b releases the connection between thesynchronization-use common storage unit 320 of the self-device, whichhas started at step S2 (step S7), and the flow returns to step S1.

By performing the above process, the MFP 2 b executes the firstoperation of performing synchronization of the setting informationbetween the setting information unit 310 and the synchronization-usecommon storage unit 320. Accordingly, the setting information shown inthe upper stage of FIG. 7 is stored in the synchronization-use commonstorage unit 320.

(Network Synchronization Operation (Second Operation))

Next, a description is given of an example of the second operation. Itis assumed that the setting information shown in the upper stage of FIG.7 is stored in the synchronization-use common storage unit 320 as aresult of the first operation. FIG. 11 is a flowchart of an example ofthe second operation of the network synchronization operation. FIG. 12is a flowchart of a detailed example of step S23 in FIG. 11.

First, the MFP 2 a determines whether the time has reached thesynchronization start time (step S21). At this step, the synchronizationcontrol unit 240 makes the determination based on a setting of“automatic synchronization interval” which is stored in thesynchronization setting information unit 230. When it is determined thetime has reached the synchronization start time (Yes in step S21), theflow proceeds to step S22. When it is determined that the time has notyet reached the synchronization start time (No in step S21), step S21 isrepeatedly performed.

In step S22, the MFP 2 a connects itself to the synchronization-usecommon storage unit 320 of the MFP 2 b, with which synchronization is tobe performed (synchronization target) (step S22). In this case, thesynchronization control unit 240 of the MFP 2 a is connected to thesynchronization-use common storage unit 320 of the MFP 2 b.

In step S23, the MFP 2 a performs a synchronization process with the MFP2 b, which is the synchronization target (step S23). In this case, itmeans that the setting information stored in the synchronization-usecommon storage unit 320 of the MFP 2 b is updated. Details of theprocess performed at step S23 are described with reference to FIG. 12.

First, the MFP 2 a starts exclusive control (step S31). Thesynchronization control unit 240 creates a directory, for example, as aprocess of exclusive control. Specifically, before startingsynchronization, the synchronization control unit 240 of the MFP 2 acreates a directory in the synchronization-use common storage unit 320of the MFP 2 b, which is the synchronization target. Only a device thathas succeeded in creating a directory is allowed to use thesynchronization-use common storage unit 320 of the MFP 2 b.

In step S32, the MFP 2 a determines whether the exclusive control issuccessfully implemented (step S32). When the exclusive control issuccessfully implemented (Yes in step S32), the flow proceeds to stepS33. When the exclusive control is unsuccessful (No in step S32), itmeans that the synchronization is unsuccessful, and the process ends as“synchronization unsuccessful”.

In step S33, the MFP 2 a compares the setting information in thesynchronization-use common storage unit 320 of the MFP 2 b, which is thesynchronization target (see upper stage of FIG. 7), with the settinginformation in the setting information unit 210 of the self-device (seelower stage of FIG. 7) (step S33).

In step S33, the synchronization control unit 240 associates differentuser IDs of the same users together, among the users of the registereduser information in the setting information unit 210 and the users ofthe registered user information in the synchronization-use commonstorage unit 320. For example, the user having the user ID of “01 a”shown in the lower stage of FIG. 7 and the user having the user ID of“01 b” shown in the upper stage of FIG. 7 have the same user name“TARO”. As described above, when the same user name is registered indifferent devices with different user IDs, it is determined that thedifferent user IDs correspond to the same user, and the different userIDs are associated with each other. When different setting informationitems are determined as being relative to the same user, the differentsetting information items are associated with each other in thesame-user information table.

In step S34, the MFP 2 a updates the setting information in thesynchronization-use common storage unit 320 of the synchronizationtarget and the setting information unit 210 of the self-device, to thelatest information (step S34). In this step, after the comparison madeat step S33, the synchronization control unit 240 updates/converts thesetting information stored in the synchronization-use common storageunit 320 and the setting information stored in the setting informationunit 210 of the self-device, to the latest information.

In step S34, the MFP 2 a is a device that has newly joined the networksynchronization system 1, and therefore, all setting information held inthe MFP 2 a is determined as being old, and the individual setting fileof each of the users is updated based on the setting information storedin the synchronization-use common storage unit 320.

Accordingly, the setting information in the lower stage of FIG. 7 ischanged to the setting information in the lower stage of FIG. 8. Theregistered user information table shown in the lower stage of FIG. 8indicates that all of the individual setting files have been updated.Furthermore, the setting information in the upper stage of FIG. 7 isupdated to the setting information in the upper stage of FIG. 8. Thesame-user information table in the upper stage of FIG. 8 indicates thatthe setting information items separately managed in the respectivedevices are associated with each other (tied together).

When step S34 is completed, the flow proceeds to step S35, where the MFP2 a ends the exclusive control that has started in step S31 (step S35).The exclusive control ends as the synchronization control unit 240erases the directory created at step S31. As the synchronization issuccessful, the process ends as “synchronization successful”.

Referring back to FIG. 11, when the synchronization process at step S23is completed, the flow proceeds to step S24, where the MFP 2 adetermines whether the synchronization process is successful (step S24).When the synchronization process is successful (Yes in step S24), theflow proceeds to step S25. When the synchronization process isunsuccessful (No in step S24), the flow proceeds to step S27.

In step S25, the MFP 2 a releases the connection between thesynchronization-use common storage unit 320 of the synchronizationtarget, which has started at step S22 (step S25). In this case, it meansthat the synchronization control unit 240 is disconnected from thesynchronization-use common storage unit 320.

Next, in step S26, the MFP 2 a updates the setting information in thesetting information unit 210 of the self-device (step S26). In step S26,in a case where the setting information unit 210 includes HDD sectionshaving exactly the same format for storing the setting information, thesynchronization results can be immediately reflected by switching theHDD section that is currently operating. The HDD section is preferablyswitched when all of the users using the MFP 2 a have logged out. Whenthe process of step S26 is completed, the flow returns to step S21 onceagain.

In step S27, the MFP 2 a releases the connection between thesynchronization-use common storage unit 320 of the synchronizationtarget, which has started at step S22 (step S27), and the flow returnsto step S21.

By performing the above process, the MFP 2 a that has newly joined thenetwork synchronization system 1 executes the second operation ofperforming synchronization between the MFP 2 b (synchronization-usecommon storage unit 320). Accordingly, the setting information shown inthe lower stage of FIG. 8 is stored in the setting information unit 210.

In the network synchronization system 1 and the MFP 2 according to thefirst embodiment of the present invention, synchronization can beperformed between MFPs connected via a network, without the use of aserver device. This is possible because each of the MFPs 2 constantlymaintains the latest setting information in the synchronization-usecommon folder disclosed in the network. Furthermore, according to thefirst embodiment, setting information of the same user whose user IDsare separately managed in different MFPs 2 can be associated with eachother (tied together), so that synchronization can be performedappropriately.

In the process of step S33, when different user IDs are given to thesame user name, it is determined that the different user IDs correspondto the same user; however, the present invention is not so limited.Other kinds of information may be uniquely given to each user, otherthan a user name. An example of another kind of information is an ICcard number, or biometric authentication information that is managed inassociation with the user. In addition to a user name, the “Windows(registered trademark) user name” and the “Windows (registeredtrademark) user password” in the individual setting information of theuser (see FIG. 3) may also be used. In this case, authentication isperformed between the MFP 2 and the information processing server 3(that is, authentication at the external server), and user informationcan be associated between the MFP 2 and the information processingserver 3 by automatically changing the user name of the user to thatmanaged in the information processing server 3.

(First modification of Network Synchronization Operation)

A description is given of a first modification of the networksynchronization operation. After the network synchronization operation,when the same new user is registered in both the MFP 2 a and the MFP 2b, network synchronization for the setting information is performedbetween the MFPs. It is assumed that setting information schematicallyshown in FIG. 13 (a user having the user name “SABURO” and a user havingthe user name “SHIRO”) is stored beforehand in the setting informationunit 210 and the setting information unit 310 of the MFP 2 a and the MFP2 b, respectively.

In this case also, the operation is performed in the order of the firstoperation described with reference to FIGS. 9 and 10 and the secondoperation described with reference to FIGS. 11 and 12. A supplementaldescription is given on steps S33 and S34 in FIG. 12.

In step S33, the MFP 2 a compares the setting information (see upperstage of FIG. 13) in the synchronization-use common storage unit 320 ofthe synchronization target with the setting information (see lower stageof FIG. 13) in the setting information unit 210 of the self-device (stepS33).

In step S33, the synchronization control unit 240 associates the sameusers together, among the users of the registered user information inthe setting information unit 210 and the users of the registered userinformation in the synchronization-use common storage unit 320. Forexample, the user having the user ID of “03 a” shown in the lower stageof FIG. 13 and the user having the user ID of “03 b” shown in the upperstage of FIG. 13 have the same user name “SABURO”. The user having theuser ID of “04 a” and the user having the user ID of “04 b” have thesame user name “SHIRO”. When the same user name is registered indifferent devices with different user IDs, it is determined that thedifferent user IDs correspond to the same user, and the different userIDs are associated with each other. When different setting informationitems are determined as being relative to the same user, the differentsetting information items are associated with each other in thesame-user information table.

In step S34, the MFP 2 a updates the setting information in thesynchronization-use common storage unit 320 of the synchronizationtarget and the setting information unit 210 of the self-device, to thelatest information (step S34). In this step, the synchronization controlunit 240 updates the individual setting files of the users based on thesetting information in the synchronization-use common storage unit 320and the setting information in the setting information unit 210 of theself-device. In this step, the last-update dates for each user arecompared with one another, and the individual setting files are updatedto the individual setting file having the latest update date. Forexample, for the user having the user name of “SABURO”, the last-updatedate of the individual setting file in the upper stage of FIG. 13 isnewer than that in the lower stage of FIG. 13, and therefore allindividual setting files for this user are updated to “File03 b”.Meanwhile, for the user having the user name of “SHIRO”, the last-updatedate in the lower stage of FIG. 13 is newer than that in the upper stageof FIG. 13, and therefore all individual setting files for this user areupdated to “File04 a”. Accordingly, the setting information in the lowerstage of FIG. 13 is changed to the setting information in the lowerstage of FIG. 14. Furthermore, the setting information in the upperstage of FIG. 13 is updated to the setting information in the upperstage of FIG. 14. Accordingly, the setting information for each user canbe synchronized between both devices.

As described above, according to the first modification, when the samenew user is registered in both the MFP 2 a and the MFP 2 b, networksynchronization for the setting information can be efficiently performedbetween the MFPs with the use of the same-user information table.

(Second Modification of Network Synchronization Operation)

A description is given of a second modification of the networksynchronization operation. After the network synchronization operation,when one of the user information items of the same user registered inboth the MFP 2 a and the MFP 2 b has been deleted from either one of theMFP 2 a or the MFP 2 b, network synchronization for the settinginformation is performed between the MFPs. It is assumed that settinginformation shown in FIG. 15 is stored beforehand in the settinginformation unit 210 and the setting information unit 310 of the MFP 2 aand the MFP 2 b, respectively (users having the user names “SABURO” and“SHIRO” are deleted from MFP 2 b).

In this case also, the operation is performed in the order of the firstoperation described with reference to FIGS. 9 and 10 and the secondoperation described with reference to FIGS. 11 and 12. A supplementaldescription is given on steps S33 and S34 in FIG. 12.

In step S33, the MFP 2 a compares the setting information (see upperstage of FIG. 15) in the synchronization-use common storage unit 320 ofthe synchronization target with the setting information (see lower stageof FIG. 15) in the setting information unit 210 of the self-device (stepS33).

In step S33, the synchronization control unit 240 associates the sameusers together, among the users of the registered user information inthe setting information unit 210 and the users of the registered userinformation in the synchronization-use common storage unit 320. In thiscase, the setting information items determined as being those of thesame user are already associated with each other in the same-userinformation table in the top stage shown in FIG. 15, and therefore anassociating process is not performed.

In step S34, the MFP 2 a updates the setting information in thesynchronization-use common storage unit 320 of the synchronizationtarget and the setting information unit 210 of the self-device, to thelatest information (step S34). In this step, the synchronization controlunit 240 updates the individual setting files of the users based on thesetting information in the synchronization-use common storage unit 320and the setting information in the setting information unit 210 of theself-device. A problem arises in how to handle a user having a user name“SABURO”, who is deleted from a first device (the MFP 2 b in thisexample), but has logged into a second device (the MFP 2 a in thisexample) after being deleted from the first device. Such a user isdetermined as capable of using the network synchronization system 1, andis therefore maintained. That is, the last login date and the deletiondate in the deleted user information table are compared, and when thelast login date is newer than the deletion date, the information isupdated such that the user name is maintained. Conversely, when the lastlogin date is older than the deletion date, it is determined that theuser is not using the network synchronization system 1 anymore, andtherefore the corresponding user name is deleted (in this example,“SHIRO”). Accordingly, the setting information in the lower stage ofFIG. 15 is changed to the setting information in the lower stage of FIG.16. Furthermore, the setting information in the upper stage of FIG. 15is updated to the setting information in the upper stage of FIG. 16. Asshown in the registered user information table in the upper stage ofFIG. 16, the user who has logged into one device after being deletedfrom another device is registered once again in the other device. Thisuser is deleted from the deleted user information table in the upperstage of FIG. 16.

As described above, according to the second modification, when one ofthe user information items of the same user registered in both the MFP 2a and the MFP 2 b has been deleted from either one of the MFP 2 a or theMFP 2 b, network synchronization for the setting information iseffectively performed between the MFPs with the use of the same-userinformation table and the deleted user information table.

The above describes the first modification and the second modificationof the network synchronization operation according to the presentembodiment. Other modifications may be made with the use of theregistered user information table, the deleted user information table,and the same-user information table. In one modification, when networksynchronization is performed between two devices, the user namecorresponding to user information items in the registered userinformation tables of both devices is renamed with “_N”. In anothermodification, among the user information items corresponding to the sameuser name in the registered user information tables of both devices, theuser information corresponding to the newest last-update date isregistered in the same-user information table. In yet anothermodification, among the user information items corresponding to the sameindividual name in the registered user information tables of bothdevices, the user's individual name with the oldest last-update date isrenamed with “_N”. In yet another modification, among the same IC cardnumbers, the IC card number corresponding to the user with the oldestlast-update date is deleted, so that the next time the correspondinguser attempts to log in, a deletion notification is made.

For example, it is assumed that a certain user prints out, with the useof a predetermined MFP, a QR cover sheet with a QR code having embeddeda user ID of the certain user managed in the predetermined MFP. This QRcover sheet can be used to log into the predetermined MFP. In thesame-user information (or authentication user information) shown in FIG.4 stored in this predetermined MFP, the setting information items of thecertain user, which are separately managed in different MFPs (thepredetermined MFP and an MFP other than the predetermined MFP), areassociated with each other.

With the above configuration, the certain user can print out, with theuse of another MFP, a QR cover sheet with a QR code having embedded auser ID of the certain user managed in the other MFP. This QR coversheet can be used to log into the predetermined MFP.

That is, when a log-in instruction (for logging into a self-device) ismade by a user registered in another MFP, this user is allowed to loginto the self-device based on individual setting information of the userregistered in the self-device that is associated with the same userregistered in the other MFP, in the same-user information (orauthentication user information) shown in FIG. 4. A reference example isdescribed in a third embodiment given below.

Second Embodiment

A description is given of a second embodiment according to the presentinvention with reference to FIGS. 17 through 20. The mechanism ofnetwork synchronization described in the first embodiment is used toeffectively apply, to the devices, update information common to thedevices (hereinafter, simply referred to as “common update information”)such as definition information for anti-virus measures and updateinformation of functions of the devices.

For example, common update information can be applied to other MFPs,simply by having a certain MFP included in the network synchronizationsystem 1 acquire common update information via a download server on theInternet and transfer it to other MFPs by network synchronization, or byhaving the common update information applied to a certain MFP and thenreflecting (transferring) the settings that are to applied to be theother MFPs by network synchronization.

(Example of System Configuration)

The network synchronization system according to the second embodimenthas the same configuration as that of the network synchronization system1 according to the first embodiment (see FIG. 1), and is not furtherdescribed.

(Example of Functional Configuration for Applying Update Information)

FIG. 17 is a functional block diagram of the MFP according to the secondembodiment. As shown in FIG. 2, the MFP 2 includes the settinginformation unit 210, the synchronization-use common storage unit 220,the synchronization setting information unit 230, the synchronizationcontrol unit 240, and a function update control unit 250. A descriptionis given of aspects that are different from those of the functionalconfiguration of the MFP according to the first embodiment (see FIG. 2).

The setting information unit 210 stores the setting information of theMFP 2. The setting information includes the above-described commonupdate information in addition to the setting information (individualsetting information) for each user described in the first embodiment.

The synchronization-use common storage unit 220 stores the settinginformation that is the target of network synchronization in the networksynchronization system 1. The setting information that is the target ofnetwork synchronization is the common update information stored in thesetting information unit 210, and this information is copied to andstored in the synchronization-use common storage unit 220.

The synchronization setting information unit 230 stores synchronizationsetting information which is setting information specifying operationsof network synchronization. An example of the synchronization settinginformation according to the second embodiment is described below withreference to FIG. 18.

The synchronization control unit 240 implements various controloperations pertaining to network synchronization based onsynchronization setting information stored in the synchronizationsetting information unit 230.

The function update control unit 250 implements control operations forupdating the functions based on synchronization setting informationstored in the synchronization setting information unit 230. For example,the function update control unit 250 updates the functions based on thecommon update information stored in the setting information unit 210 andthe synchronization-use common storage unit 220.

With the above functional configuration, the network synchronizationsystem 1 according to the second embodiment can effectively apply, tothe devices, common update information such as definition informationfor anti-virus measures and update information of functions of thedevices.

The synchronization control unit 240 and the function update controlunit 250 are not clearly distinguished. They may be collectivelyreferred to as a control unit 260, as they are both function units forcontrolling operations pertaining to network synchronization. In thisembodiment, the synchronization control unit 240 and the function updatecontrol unit 250 are described separately, but other embodiments of thepresent invention may have modified designs.

(Example of Synchronization Setting Information Used for NetworkSynchronization)

FIG. 18 illustrates an example of synchronization setting informationused for network synchronization. This synchronization settinginformation is stored in the synchronization setting information unit230. Based on such synchronization setting information, thesynchronization control unit 240 or the function update control unit 250implements various control operations for performing networksynchronization or for updating functions. In the following, eachsetting item is described in association with control operationsperformed by the synchronization control unit 240 or the function updatecontrol unit 250.

The “last-update date setting” and the “network synchronization setting”are the same as those in the first embodiment (see FIG. 5), and are notfurther described.

A description is given of the “settings pertaining to updateinformation”. The “settings pertaining to update information” specify,for example, whether to automatically download (transfer) common updateinformation in the self-device, or whether to automatically perform anupdate operation (apply common update information) based on the commonupdate information.

“(Perform or do not perform) automatic download” is a setting itemspecifying whether to automatically download common update informationin the self-device. Based on this setting item, the synchronizationcontrol unit 240 may prevent the common update information stored in asynchronization-use common folder (for example, the synchronization-usecommon storage unit 320) of another device from being automaticallydownloaded, or from being downloaded at all.

The “download method (via download server or via networksynchronization)” is a setting item for specifying whether the commonupdate information is to be downloaded to the self-device via a downloadserver or via network synchronization. When this setting item isspecifying “via network synchronization”, the synchronization controlunit 240 downloads the common update information stored in asynchronization-use common folder (for example, the synchronization-usecommon storage unit 320) of another device. When this setting item isspecifying “via a download server”, the synchronization control unit 240downloads the common update information from the Internet or from theinformation processing server 3 if the information processing server 3is the download server. Accordingly, this is a selection unit whichmakes it possible to select whether the information is to be downloadedvia network synchronization or via a download server.

When “via a download server” is specified for this setting item in afirst device, the first device can be configured such that “disclose” isautomatically set as the setting item of “disclose synchronization-usecommon folder”. In this case, in other devices, “via networksynchronization” is specified (“via a download server” is prevented frombeing specified). Accordingly, all of the other devices can acquire thecommon update information from the synchronization-use common folderdisclosed by the first device. That is, the common update informationacquired via a download server such as the Internet by the first deviceincluded in the network synchronization system 1 can be transferred tothe other devices by network synchronization. Accordingly, the workloadon the network can be reduced between the network synchronization system1 and external devices.

The “automatic execution interval (for example, 24 through 999 hours)”is a setting item for specifying the execution intervals ofautomatically downloading the common update information in theself-device. The synchronization control unit 240 automaticallydownloads the common update information at the specified automaticexecution intervals. The automatic execution interval can be specifiedby the user. The automatic execution interval can also be specified bycalculating the probability according to random numbers based on themachine-specific number and the present time for distributing thenetwork load, and determining the next execution time from an executioninterval probability X.

“(Perform or do not perform) automatic update” is a setting itemspecifying whether the self-device is to automatically perform an updateoperation based on the common update information stored in theself-device. When “perform” is specified in “automatic download” and“perform” is specified in “automatic update”, the function updatecontrol unit 250 automatically performs an update operation based on thecommon update information automatically downloaded by thesynchronization control unit 240.

“(Perform or do not perform) manual update” is a setting item specifyingwhether the self-device is to manually perform an update operation basedon the common update information stored in the self-device. When“perform” is specified in “automatic download” and “perform” isspecified in “manual update”, the synchronization control unit 240automatically downloads the common update information and stores it inthe setting information unit 210 of the self-device. However, the updateoperation based on the common update information is performed manually,and therefore the user of the self-device determines the quality of thedownloaded common update information and instructs the function updatecontrol unit 250 to perform the update operation accordingly. Wheneither one of “automatic update” and “manual update” is specified as“perform”, the other one is specified as “do not perform”. Accordingly,it can be selected whether to perform the update operation automaticallyor manually.

The “version selection (select from downloaded version)” is a settingitem for selecting which version of common update information is to beused by the self-device for the update operation among the pluralversions of the common update information stored in the self-device,i.e., for selecting the version used for the update operation.Typically, the version of the common update information is continuouslyupdated by the issuing source. Under such circumstances, the latestversion of common update information is not always appropriate for theupdate operation. The safety in using the common update information ofeach version is preferably confirmed before applying it to the device.Thus, when “perform” is specified in “manual update” and “perform” isspecified in “version selection”, the user can select which version ofcommon update information is to be applied to the self-device by manualupdate.

“Reflect version selection in network synchronization (reflect or do notreflect)” is a setting item specifying whether the setting of the“version selection (select from downloaded version)” is to be reflectedin the other devices. For example, when “perform” is specified in“manual update” and “do not reflect” is specified in “reflect versionselection in network synchronization”, the update operation is performedmanually. Then, the setting of “reflect version selection in networksynchronization” is changed to “reflect”, and the synchronizationcontrol unit 240 uses the mechanism of network synchronization toreflect the “version selection” of the own-device to another device.Accordingly, the other device performs network synchronization betweenthe self-device to perform the update operation based on the sameversion of update information as that of the self-device.

“Notify download/upload (notify or do not notify)” is a setting item forspecifying whether to notify the user, for example, by e-mail, that thedownloading of the common update information and/or the updating basedon the common update information has been completed in the self-device.When “notify” is specified, a notification is sent to the user with ane-mail generated based on contents set with setting items of “subject(for example, displaying 01 through 256 characters)” and “main text (forexample, displaying 01 through 2,048 characters)”. Sentences areprepared beforehand, such as “Download completed on Month/Day/Time” asthe subject and “The download has been completed at Month/Day/Time. Thefollowing contents have been downloaded.” as the main text. The functionupdate control unit 250 uses these to send a notification to the user.When “perform” is specified in “automatic download” and “perform” isspecified in “manual update”, after the common update information isdownloaded, the user who has received a notification by e-mail performsa manual update operation based on the downloaded common updateinformation.

Next, a description is given of “settings for automatic reboot”. The“settings for automatic reboot” is for specifying whether theself-device is to be automatically rebooted.

“(Perform or do not perform) automatic reboot” is a setting itemspecifying whether the self-device is to be automatically rebooted. Forexample, when an update based on the common update information is to beprovided when the self-device is rebooted, this setting item isspecified as “perform”.

The “automatic reboot time (for example, 00:00 through 23:59)” is asetting item for specifying the time when the self-device is to beautomatically rebooted. When “perform” is specified in “automaticreboot”, the function update control unit 250 automatically reboots theself-device at the specified execution time. When an update based on thecommon update information is to be provided at the time when theself-device is rebooted, the update based on the common updateinformation is performed at the same time as when the self-device isrebooted. This execution time may be specified by the user. A time whenthe self-device is unlikely to be in use (for example, 04:00) may bespecified.

The synchronization setting information shown in FIG. 18 is describedabove. Based on such synchronization setting information, thesynchronization control unit 240 implements various control operationspertaining to network synchronization. The function update control unit250 implements control operations for updating the functions, based onthe settings for update information in the synchronization settinginformation.

Accordingly, the following advantages are achieved. That is, commonupdate information can be applied to other MFPs, simply by having acertain MFP included in the network synchronization system 1 acquirecommon update information via a download server on the Internet andtransfer it to other MFPs by network synchronization, or by applying thecommon update information to a certain MFP and then reflecting thesettings that are to applied including the version information to theother MFPs by network synchronization.

A description of the operations of network synchronization is givenbelow. First, a description is given of an operation for downloading(acquiring/transferring) the common update operation, and then adescription is given of an update operation. These operations aredescribed with reference to the system configuration shown in FIG. 6.

(Network Synchronization Operation (Download))

An operation of downloading the common update information is described.Specifically, in the MFP 2 b, “via download server” is specified in“download method” of FIG. 18, and the MFP 2 b downloads the commonupdate information via the download server. Then, the common updateinformation is uploaded to the synchronization-use common storage unit320 of the self-device.

The operation of network synchronization (downloading via the downloadserver) performed by the MFP according to the second embodiment is thesame as that of the first embodiment (see FIG. 9). However, thesynchronization process (step S3 in FIG. 9) is different, and thereforea description is given of the synchronization process. FIG. 19 is aflowchart of an example of the synchronization process (downloading viathe download server) according to the second embodiment.

The processes of steps S41 through S46 shown in FIG. 19 are the same asthose of steps S11 through S15 shown in FIG. 10 with the exception ofstep S43, and therefore a description is given only for step S43.

In step S43, the MFP 2 b uploads the common update information (stepS43). The synchronization control unit 340 of the MFP 2 b uploads, intothe synchronization-use common storage unit 320, the common updateinformation that it has downloaded. By performing this process, anotherMFP (for example, the MFP 2 a) can acquire the common update informationfrom the synchronization-use common storage unit 320 by networksynchronization.

Next, a description is given on how the MFP 2 a, in which “via networksynchronization” is specified in “download method” of FIG. 18, downloadsthe common update information from the MFP 2 b by networksynchronization.

The operation of network synchronization (downloading via networksynchronization) performed by the MFP according to the second embodimentis the same as that of the first embodiment (see FIG. 11). However, thesynchronization process (step S3 in FIG. 11) is different, and thereforea description is given of the synchronization process. FIG. 20 is aflowchart of an example of the synchronization process (downloading vianetwork synchronization) according to the second embodiment.

The processes of steps S51 through S56 shown in FIG. 20 are the same asthose of steps S31 through S35 shown in FIG. 12, with the exception ofstep S53, and therefore a description is given only for step S53.

In step S53, the MFP 2 a downloads the common update information (stepS53). The synchronization control unit 240 downloads the common updateinformation from the synchronization-use common storage unit 320. Byperforming this process, a certain MFP included in the networksynchronization system 1 can transfer the common update informationacquired via a download server such as the Internet, to other MFPs, bynetwork synchronization.

(Example of Network Synchronization Operation (Manual Update))

Next, a description is given of the update operation based on the commonupdate information. When “perform” is specified in “automatic update” ofFIG. 18, the update is automatically performed when the device isrebooted, and therefore no further descriptions are made regarding“automatic update”.

When “perform” is specified in “manual update” and “do not reflect” isspecified in “reflect version selection in network synchronization” inthe MFP 2 b, after the update is performed manually in the MFP 2 b,“reflect version selection in network synchronization” is changed to“reflect”. Then, the synchronization control unit 340 of the MFP 2 brenews the information pertaining to the “version selection” in thesynchronization-use common storage unit 320.

Another MFP (for example, the MFP 2 a) can acquire the informationpertaining to “version selection” from the synchronization-use commonstorage unit 320 by network synchronization with the MFP 2 b. Then, theother MFP 2 a may perform the update operation based on the commonupdate information indicated by the “version selection” when it isrebooted.

By performing the above process, common update information can beapplied to other MFPs, simply by applying the common update informationto a certain MFP included in the network synchronization system 1, andthen reflecting the settings that are to be applied including theversion information, to the other MFPs by network synchronization.

Third Embodiment

A description is given of a third embodiment according to the presentinvention with reference to FIGS. 21 through 25. The mechanism ofnetwork synchronization described in the first embodiment is used toassociate the same setting information managed separately in twodifferent MFPs. A predetermined user can print out, with a certain MFP,a sheet (QR cover sheet) including a QR code recording the user ID ofthe user managed in the certain MFP, for logging into the certain MFP.With the use of this sheet, the user can log into the certain MFP andalso another MFP. That is, when an instruction for logging into theself-device is received from a user of another MFP, the user of theother MFP can log into the self-device based on user information in theself-device that is associated with the user of the other MFP, in theuser authentication information shown in FIG. 4.

In the following description, the user ID constitutes one of theidentification information items recorded in the QR code shown in FIG.24.

(Configuration of Device)

FIG. 21 is a block diagram of the MFP according to a third embodiment ofthe present invention. As shown in FIG. 21, the MFP 2 is connected, viaa bus, to an external storage device 14, an external medial input outputdevice 15, a printing device 16, an image scanning device 17, a displaydevice 18, and an input device 19.

When the MFP 2 exchanges fax data with another fax machine via a faxline 21, the MFP 2 is connected to an external device via the Internet22 through communication control units 23 such as a modem and a router,and connects to a personal computer (hereinafter, “PC”) 24 and a servercomputer (hereinafter, “server”) 25 in a wired or wireless manner toexchange information.

The MFP 2 includes a CPU (Central Processing Unit) (not shown) forcontrolling the various devices connected to the MFP 2, a memory unitincluding a ROM (Read Only Memory) and a RAM (Random Access Memory), afax control unit, a LAN control unit, an input/output device controlunit, a storage device control unit, an image processing control unit,and an input control unit. Furthermore, the MFP 2 includes a storagedevice including a built-in hard disk drive (hereinafter, “HDD”)connected to the storage device control unit, a print control unitconnected to the image processing control unit, an image scanningcontrol unit, and a display control unit.

The external storage device 14 is a storage device such as an externalHDD (Hard Disk Drive). The external medial input output device 15 is forinputting/outputting information to/from media such as a multimedia card(registered trademark), smart media (registered trademark), a memorystick (registered trademark), an SD memory card (registered trademark),a CD-ROM, a floppy disk (registered trademark), and a USB memory(registered trademark).

The printing device 16 is an output device such as a laser printer or aninkjet printer for performing monochrome printing, color printing, anddouble-sided printing. The image scanning device 17 is for scanning anoriginal image by an optical process to obtain electronic data. Thedisplay device 18 is an output device including a touch panel, a CRT,and a liquid crystal display.

The input device 19 is for inputting information with a touch panel andkeybuttons. The input device 19 can be a microphone for inputtinginformation by sound.

As described above, the MFP 2 according to the third embodiment controlsthe various devices connected to (or included in) the MFP 2.

The MFP 2 implements control to identify the image information acquiredwith the image scanning device 17 in accordance with identificationinformation included in the image information, and to output (or store)the image information. The identification information is for identifyingan output file name (or a saving file name) in the computer. The MFP 2performs a process of outputting the image information by applying theidentification information included in the image information acquired bythe image scanning device 17 as the output file name.

Accordingly, when the image information is output (or stored), theidentification information of the image information (for example, headerinformation) can be effectively set. Detailed configurations aredescribed below with reference to FIG. 22.

(Functional Configuration)

FIG. 22 is a functional block diagram of the MFP according to the thirdembodiment. The arrows between the blocks in FIG. 22 indicate arepresentative flow of signals, but do not limit the functions of theblocks.

As shown in FIG. 22, the MFP 2 includes an image information acquiringunit 101, an image information recognizing unit 102, an identificationinformation recognizing unit 103, an output control unit (storagecontrol unit) 104, and a storage device 105.

The image information acquiring unit 101 acquires image information. Forexample, the image information acquiring unit 101 acquires imageinformation scanned by the image scanning device 17; image informationstored in the external storage device 14, the external medial inputoutput device 15, or the storage device 105; image information receivedfrom an external device connected via the Internet 22; and imageinformation based on fax data received from another fax machine via thefax line 21.

The image information recognizing unit 102 recognizes image informationacquired by the image information acquiring unit 101. The identificationinformation recognizing unit 103 recognizes identification informationincluded in the image information acquired by the image informationacquiring unit 101. For example, the identification informationrecognizing unit 103 recognizes the identification information based onan optical scanning code such as a QR code (registered trademark)included in the image information. The identification information isused for identifying the image information in a computer, such as anoutput file name (or a saving file name) relevant to the outputting (orstoring) operation performed by the output control unit (storage controlunit) 104 described below.

The output control unit (storage control unit) 104 identifies the imageinformation recognized by the image information recognizing unit 102according to the identification information recognized by theidentification information recognizing unit 103, and outputs (or stores)the image information. For example, header information which isidentification information is added to the image information, and animage is formed on a recording medium by the printing device 16. Inanother example, the identification information may be added to the filename or the subject name of an electronic file generated based on theimage information, and an output operation is performed to send theimage by fax transmission to another fax device via the fax line 21, orto send the image to an external device connected via the Internet 22.Furthermore, identification information is added to the file name(including a document name or a category name) of the electronic filegenerated based on the image information, and the electronic file isstored in the storage device 105.

With the above functional configuration, the MFP 2 identifies the imageinformation acquired by the image scanning device 17 according to theidentification information included in the image information, andoutputs (or stores) the image information.

(Example of Operation)

FIG. 23 is a flowchart of an example of an operation performed by theMFP according to the third embodiment. A description is given of anexample of an operation performed by the MFP 2 for outputting (orstoring) the image information acquired by the image scanning device 17,with reference to the functional block diagram shown in FIG. 22.

First, the image information acquiring unit 101 acquires imageinformation (step S61). Specifically, the image information acquiringunit 101 acquires image information scanned by the image scanning device17; image information stored in the external storage device 14, theexternal medial input output device 15, or the storage device 105; imageinformation received from an external device connected via the Internet22; and image information based on fax data received from another faxmachine via the fax line 21. FIG. 24 illustrates an example of acquiredimage information. The image information used in the third embodiment isimage data having a secondary code such as a QR codes recorded at apredetermined position as shown in FIG. 24.

In step S62, the identification information recognizing unit 103determines whether the image information acquired at step S61 includesidentification information (step S62). The identification informationis, for example, an output file name (or a saving file name), which isused for identifying the image information in a computer, as describedabove. In this example, the predetermined character string included inthe QR code shown in FIG. 24 is used as the identification information.

When there is identification information (Yes in step S62), the flowproceeds to step S63, where the identification information recognizingunit 103 recognizes the identification information from the imageinformation (step S63). In this example, the predetermined characterstring included in the QR code shown in FIG. 24 is recognized. Whenthere is no identification information (No in step S62), the processends.

In step S64, the image information recognizing unit 102 recognizes theimage information acquired at step S61 (step S64). In this example, theimage information shown in FIG. 24 is recognized. Next, in step S65, theoutput control unit 104 outputs (or stores) the image informationrecognized at step S64 according to the identification informationrecognized at step S63 (step S65). FIGS. 25A through 25C illustrateprocesses of outputting or storing image information according toidentification information.

In step S65, the predetermined character string recognized at step S63is added as header information to the image information, and an image isformed on a recording medium by the printing device 16 (see FIG. 25A).In another example, identification information is added to the file nameor the subject name of the electronic file generated based on imageinformation, and an output operation is performed to send the image byfax transmission to another fax device via the fax line 21, or to sendthe image to an external device connected via the Internet 22 (see FIG.25B). In yet another example, identification information is added to thefile name (including a document name or a category name) of theelectronic file generated based on the image information, and theelectronic file is stored in the storage device 105 (see FIG. 25C).

By performing the above process, the MFP 2 identifies the imageinformation acquired by the image scanning device 17 according to theidentification information included in the image information, andoutputs (or stores) the image information. Accordingly, by recordingbeforehand an output file name (or a saving file name) in atwo-dimensional code such as a QR code as shown in FIG. 24, theidentification information of the image information can be effectivelyset when outputting (or storing) the image information.

The present invention is not limited to the specifically disclosedembodiment, and variations and modifications may be made withoutdeparting from the scope of the present invention.

The present application is based on Japanese Priority Patent ApplicationNo. 2008-070380, filed on Mar. 18, 2008, the entire contents of whichare hereby incorporated herein by reference.

1. A network synchronization system comprising plural informationprocessing devices, wherein: a first information processing device amongthe plural information processing devices comprises asynchronization-use common storage unit configured to copy and storefirst individual setting information for each user registered as beingauthorized to use the first information processing device, so that thefirst individual setting information can be shared with another one ofthe plural information processing devices other than the firstinformation processing device; and a second information processingdevice among the plural information processing devices comprises asetting information unit configured to store second individual settinginformation for each user registered as being authorized to use thesecond information processing device, and a synchronization control unitconfigured to compare the second individual setting information for eachuser stored in the setting information unit with the first individualsetting information for the corresponding user stored in thesynchronization-use common storage unit, and to update the secondindividual setting information to latest individual setting informationfor each user based on a result of the comparison, wherein thesynchronization control unit acquires common update information that iscommon to the plural information processing devices, wherein the commonupdate information is stored in the synchronization-use common storageunit.
 2. The network synchronization system according to claim 1,wherein: the common update information comprises definition informationof antivirus software or update information pertaining to a function ofthe plural information processing devices.
 3. The networksynchronization system according to claim 1, wherein: thesynchronization control unit is configured to select whether to acquirethe common update information stored in the synchronization-use commonstorage unit, or to acquire the common update information from an updateinformation server connected to the network synchronization system via anetwork.
 4. The network synchronization system according to claim 1,wherein: the second information processing device further comprises afunction update control unit configured to select whether to perform anupdate operation based on the common update information, in an automaticmanner or a manual manner.
 5. An information processing device includedin a network synchronization system comprising plural informationprocessing devices, the information processing device comprising: asetting information unit configured to store first individual settinginformation for each user registered as being authorized to use theinformation processing device; and a synchronization control unitconfigured to compare the first individual setting information for eachuser stored in the setting information unit with second individualsetting information for the corresponding user stored in asynchronization-use common storage unit included in another one of theplural information processing devices, and to update the firstindividual setting information for each user stored in the settinginformation unit to latest individual setting information for thecorresponding user based on a result of the comparison, wherein: thesynchronization control unit is further configured to acquire commonupdate information that is common to the plural information processingdevices, wherein the common update information is stored in thesynchronization-use common storage unit included in the other one of theplural information processing devices.
 6. The information processingdevice according to claim 5, wherein: the common update informationcomprises definition information of antivirus software or updateinformation pertaining to a function of the plural informationprocessing devices.
 7. The information processing device according toclaim 5, wherein: the synchronization control unit is configured toselect whether to acquire the common update information stored in thesynchronization-use common storage unit included in the other one of theplural information processing devices, or to acquire the common updateinformation from an update information server connected to the networksynchronization system via a network.
 8. The information processingdevice according to claim 5, further comprising: a function updatecontrol unit configured to select whether to perform an update operationbased on the common update information, in an automatic manner or amanual manner.